INPUTUNIVERSAL
Guide · 0.6.8

Set up your first macro.

Pick an output, choose how it runs, then enable the section.

1. Install and open

  1. Extract the whole ZIP.

    Keep InputUniversal.exe, its UI folder and DLLs together in a permanent folder. Exit any old copy from the Windows tray first.

  2. Open InputUniversal.exe.

    If WebView2 is missing, install the Microsoft WebView2 Runtime. Controller output also needs the setup below.

  3. Start with a simple setup.

    On Hold, choose Timed hold, an output and a duration. Bind your shortcut, enable the section, then tap the shortcut.

2. Bind your controls

Output is what the app presses. The section’s shortcut starts or holds the macro. The separate Enable / disable shortcut controls whether the section is enabled.

  1. Click the shortcut’s binding control, or the separate Bind button beneath Enable / disable shortcut.
  2. Press a keyboard key, modifier combination, mouse button or controller button. The assigned name appears.
  3. Press Escape to cancel. Capture also times out after 15 seconds. F6, F7 and F8 alone are reserved.

Arrow keys move between app controls; Enter or Space activates focused buttons. Clicks on app controls and typing in fields stay available while editing. If the enable binding matches the macro shortcut, the macro takes priority once enabled; F8 still stops it. Shift + F8 is the default enable/disable shortcut. After an F8 emergency stop, it stays blocked until you re-enable in the app.

3. Choose how the macro runs

Hold → Timed hold

Choose an output and duration. Enable the section, then tap its shortcut. The output releases after the duration, or when you tap the shortcut again.

Click → Tap to start / stop

Set the output, interval and total clicks. Enable the section and tap the shortcut to begin. Tap again to stop. The total is limited to 99,999.

Click → Repeat while held

Choose My bound shortcut, LMB + RMB together, LT + RT together, or LB + RB together under Held buttons. Repeating starts while the required controls are held and stops when released. The click limit applies per hold; release and press again after reaching it.

Example: output Left mouse button, mode Repeat while held, bound shortcut Left click. For controller testing, start with a 100 ms interval; short pulses can be missed by a game or viewer.

Current KBM interface with Repeat while held and LMB plus RMB selected

Mouse pull + repeat together

  1. Hold → Mode → Mouse pull.

    Set the downward rate in relative mouse units per second. Turn on Mouse pull enabled.

  2. Click → Repeat while held.

    Set Held buttons to LMB + RMB together. Choose the output, interval and total, then click Enable section.

  3. Hold both mouse buttons.

    Pull and repeat run together. Release either button to stop both. F8 locks them off.

Mouse pull is independent and can also accompany recorded playback. Timed hold, click and playback still share one main macro engine and run one at a time. Mouse pull results depend on the target’s input handling and sensitivity.

Mouse pull rate and independent enable switch

Record and replay

  1. Open Record. Choose Desktop cursor for screen positions or Game camera (relative) for movement deltas. Make a fresh recording when changing the movement mode.
  2. For controller actions, connect first and enable Include controller. Old recordings made without this contain no controller movements.
  3. Press Record or F6, wait for the three-second countdown, perform your actions, then press F6 to finish.
  4. Press Play or F7 to replay after a countdown. Adjust speed and loops as needed. F7 cannot bypass an F8 emergency lockout.

Game-camera playback has not been verified in every game. Recording can capture private typing; do not record passwords.

Save setups once

Click Save preset at the top, enter a name and save. The preset keeps settings and the current recording together. Open the preset menu to load another setup.

The last setup and completed recording recover automatically after reopening, with shortcuts off. Save named presets to retain multiple versions. Enable/disable bindings and controller tuning are saved separately.

Share a profile through Community

Browse and import profiles, or explicitly publish your own. Published profiles are public and downloadable. Imports stay stopped. Review recordings before publishing; My uploads lets you remove posts from the same PC.

Controller setup

For Xbox/XInput-compatible controllers on a Windows PC. Keyboard and mouse macros do not need these controller drivers.

  1. In the extracted Drivers folder, install ViGEmBus_1.22.0_x64_x86_arm64.exe. Restart if requested.
  2. Install HidHide_1.5.230_x64.exe if you need to prevent duplicate physical controller input.
  3. In HidHide’s Applications list, allow the exact InputUniversal.exe you extracted. Update this entry if you move the app.
  4. Hide the physical controller, leave the virtual Xbox controller visible and enable hiding. Follow the official illustrated setup guide.
  5. Reconnect the controller. Open Controller setup in InputUniversal, scan, select the physical device and connect.
  6. With games closed, use Test X or Test RT. Then open your game. In an external controller viewer, select the virtual Xbox device.

Xbox and GameSir controllers must expose XInput. Native PlayStation/DirectInput-only modes and consoles are not supported directly. If a physical Xbox interface remains visible, see the HidHide Xbox interface instructions.

Tuning, closing and troubleshooting

Does tuning stay active after closing?

Closing the app window hides it to the tray beside the clock. Tuning can continue while it runs. Exit from the tray fully quits and stops tuning; saved settings load next time. Hardware DPI and keyboard actuation are not supported.

The app is open but I can’t see it

Open its icon in the Windows tray. Exit there before launching a replacement copy.

The counter increases but the game does nothing

The counter measures presses sent by the macro, not actions accepted by the game. Check HidHide: the game must see the virtual controller without a duplicate physical controller holding the same button. Start with a 100 ms interval. Game polling and input support vary.

The graphic misses fast button presses

The controller graphic displays app output. A screen cannot show every very short press separately, so rapid presses can look like a continuous highlight. Increase the interval when checking output in a game or viewer.

My shortcut does nothing after F8

This is intentional. F8 locks macros off. Click the re-enable control in the app; keyboard, mouse and controller bindings cannot unlock it.

Does every game support this?

No. Windows output checks passed, but game compatibility varies. Follow the game’s rules. There is no green-meter detection or guaranteed recoil result.